Control Accounts

Depending on the work scope and management needs, control accounts may be at different levels in the WBS. For example, one leg of the WBS may be at level 3 and another leg may be at level 4. The level of complexity or risk factors may require additional levels of detail for management visibility and control.

A project organization structure or OBS identifies the internal hierarchical structure established for managing the work effort defined in the WBS. The lowest level of the structure identifies the organization entity such as a functional organization, work team, or person responsible for a single WBS element. An OBS is required for the Integrated Program Management Data and Analysis Report (IPMDAR) Data Item Description (DID) that is placed on contracts with earned value management reporting requirements. In the proposal or planning phase of a project, the assigned team or person are responsible for estimating or managing the WBS technical scope of work, the schedule of tasks and resources required to complete the work effort, and the time phased budget for the work effort. In the execution phase of a project, the assigned team or person are also responsible for tracking work progress; managing changes to the scope, schedule, budget, and resource requirements; and maintaining the estimate to complete for the remaining work.

Once you identify the control accounts in the ProjStream software tools, they play an important role in the workflow process and producing reports. Workflow roles are assigned at the control account level and the workflow process is initiated for the control account. Workflow form revision numbers are specific to the workflow process, project, and control account. Control accounts determine the summary level for the detailed work package and resource assignment data in the basis of estimate (BOE), baseline change request (BCR), and work authorization forms. Control accounts are a defined summary level that can be selected when producing data views or reports.